Conversation
|
Thanks for the PR! Adding a new language has a non-negligible cost in terms of compute resource for the server. Can we wait until there's some more translation activity for Hungarian? A |
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
I understand, but I would rather not. Firstly, there are languages built with much less completion than the current Hungarian (e.g. Bengali, and currently Indonesian [which is 0% at the moment]), and secondly there are languages built currently that have not had activity in over a year. Secondly, I hope to get a new coordinator, I believe that building it already will be very valuable in this process, as it shows a lot about the project. I think that limiting it to HTML generation for now would also be acceptable. |
I agree. Each new language adds an hour or two to the full build time (re:https://discuss.python.org/t/removing-non-html-pdf-epub-etc-documentation-downloads/101343/32) and means updates take longer for the active languages. This is about adding a language which has no active translator, and the last translation was in 2017(!). Even if HTML only, that's still a significant amount of time. Let's revisit when a new translator becomes active? |
|
Shall we close this for now -- as Hugo says, we can revisit later once the translation becomes more active. HTML only would probably be a good first step. A |
Name per Google's language switcher